Documenting Process and Control Changes If a process or control has changed significantly, you can document the reasons for the change in MIC.
Before you actually apply the documented change in the process catalog, you can first have the documented change approved.
In Customizing for MIC, values and names were entered for the following attributes in the
Edit Attribute Values
IMG activity:
For values for the
Change Type,
choose
You can copy SAP sample entries by activating the BC set for this IMG activity.
For naming the
Approval Status,
choose
If you want to have changes approved, then the indicator for that must be set in Customizing. Choose . The organizational unit can overwrite this central setting when it copies the processes.
The person granting approval has authorization for one of the following tasks:
Approve Documentation of Process Change (VALI-PRCHD)
Approve Documentation of Control Change (VALI-PSCHD)
In the Web applications
Process and Account Groups of the Org Unit
and
Documentation of Controls,
you can make several entries describing each change made to a process or control that was carried forward. You make these entries on the
Changes
tab page.
For each entry, you select a value for the attribute
Change Type
and specify the date from which the change is valid. Examples of change types would be
Personnel Change
or
Change in Technology
(values in the delivered BC Set). Furthermore, you can enter a detailed description of the change.
Once you have entered all your data, you trigger the approval process.
The procedure for a change requiring approval is outlined below:
On the
Changes
tab page, you document how and why the control or process changed. Then you choose
Request Approval
.
Then the workflow sends a task to the person, who has authorization for the task of approving the process change or control change.
This person approves the change.
You apply the change of the process or control in MIC.